Fix issue where UDP Exporter throws error in async callback, which isn't caught #289
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
In UDP Exporter, when sending via the socket, our callback method will rethrow the error if there an error from the
send. However, this is done asynchronously, so it isn't actually caught in the surroundingtry/catch.This
errcan happen when the UDP Packet size limit is reached. When this error is thrown, it can cause the following error in Lambda:Description of changes:
try/catch.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.